Skip to content

Update sqlparser for MATCH_RECOGNIZE exclusions - #100

Merged
osipovartem merged 1 commit into
embucket-sync-df55.0.0from
df55-match-exclusion-parser-pin
Sep 17, 2026
Merged

osipovartem merged 1 commit into
embucket-sync-df55.0.0from
df55-match-exclusion-parser-pin

Conversation

@osipovartem

Copy link
Copy Markdown
Collaborator

Summary

  • update the DataFusion 55 branch to the merged sqlparser exclusion fix
  • keep DataFusion and downstream users on a single sqlparser crate identity

Dependency PR: Embucket/datafusion-sqlparser-rs#30

Validation

  • cargo +1.95.0 check -p datafusion-sql --locked
  • cargo +1.95.0 fmt --all -- --check
  • lockfile changes are limited to the sqlparser and sqlparser_derive revisions

@osipovartem

Copy link
Copy Markdown
Collaborator Author

CI triage: the three failing checks are inherited from the base commit dbada1cc1fbce6bb8fa98bf67dd6dba2196a8322. That commit has the same failures: cargo test datafusion-cli (amd64), clippy, and check configs.md and ***_functions.md is up-to-date. This PR changes only the sqlparser revision in Cargo.toml/Cargo.lock. Focused validation passed with cargo +1.95.0 check -p datafusion-sql --locked and cargo +1.95.0 fmt --all -- --check; the referenced parser PR passed stable, beta, compile, lint, docs, and RAT checks.

@osipovartem
osipovartem merged commit 90a492f into embucket-sync-df55.0.0 Sep 17, 2026
32 of 35 checks passed
@osipovartem
osipovartem deleted the df55-match-exclusion-parser-pin branch September 17, 2026 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant